Skip to content

Audience parameter support#164

Open
linglingye001 wants to merge 2 commits intorelease/v2.6.0from
linglingye/audience-support
Open

Audience parameter support#164
linglingye001 wants to merge 2 commits intorelease/v2.6.0from
linglingye/audience-support

Conversation

@linglingye001
Copy link
Member

@linglingye001 linglingye001 commented Mar 11, 2026

Usage

helm install azureappconfiguration.kubernetesprovider \
    oci://mcr.microsoft.com/azure-app-configuration/helmchart/kubernetes-provider \
    --namespace azappconfig-system \
    --create-namespace
    --set audience="https://appconfig.sovcloud-api.fr"

targetCPUUtilizationPercentage: 80
targetMemoryUtilizationPercentage: 80

audience: ""
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How about put it into env section and name it "azureAppconfigAudience"

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can use full product name. If put it to the env section , the command will be --set env.azureAppConfigurationAudience, what do you think? @zhenlan

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Which one is more consistent with existing naming conventions?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Helm best practice recommended camelCase, and azureAppConfigurationAudience is more descriptive, consistent with how azureClientId and azureTenantId are already done.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants